The on-board diagnosis consists essentially of the monitoring of the sensors and actuators connected to the controller, the plausibility check, the evaluation of current states and signals against target values, characteristic curves or algorithms, and the failure monitoring of cyclically-incoming information such as connected CAN systems and their data.
The controllers perform this self-monitoring during ongoing operation. If one or several error(s) are detected, the results are saved in the event memory of the controller as Diagnostic Trouble Codes (DTCs). Later, these can be read out using the diagnostic tester.
In case of safety-relevant errors, they are displayed to the driver on the dashboard.

Off-board diagnosis is free troubleshooting. After the diagnostics tester has read the data stored in the controller (including the DTCs), they are supplemented by additional information such as test instructions or wiring diagrams. With these test instructions, it should be possible to remedy all problems detected in the on-board diagnosis. Furthermore, there are errors which extend beyond the system limits of on-board diagnosis. Therefore, off-board diagnosis offers special test procedures for the analysis of sensors and actuators.

Example: A sticking solenoid valve does not cause an electrical error (since it is electrically OK) and thus cannot be detected by on-board diagnosis. The diagnostic tester therefore offers the actuator test test procedure. This enables a service technician to check the mechanically-correct functioning of the solenoid valve.

EOL diagnosis is used for commissioning a vehicle. Here, the functionality of the controller is configured and calibrated.

The link between on-board diagnosis and off-board diagnostic tools is diagnostic communication. Using standardized hardware and software interfaces, the controllers installed in the vehicle connect to the diagnostic tester.
The diagnosis of Voith vehicle components is currently carried out under the KWP2000 (on K-Line hardware) and UDS (on CAN-BUS) protocols. Both hardware and protocol are strictly standardized, since a multitude of controllers are installed in each vehicle, which can all be addressed by an OEM diagnostic tester (e.g. MAN-Cats STARdiagnose). In addition, there are legal regulations for the diagnosis, which are derived, for example, from the emissions regulations (OBD2).
Essentially, the diagnostic communication runs as a "question/answer game". A client/server model underlies this. The controller functions as a server and the tester as client. Since all controllers and testers are connected together on one line, each device is assigned a physical address.

To use the ALADIN diagnostic software, you need a PC which meets the system specifications, a diagnostics interface (level converter) and, optionally, a vehicle-side adapter plug.

Diagnostics interfaces are available in different versions. Please check which one meets your requirements on the Interface page.

The primary function in ALADIN is to read the event memory and its visualization in the Reporter. Reading is carried out via the Upload function. All of the controller data are read and stored in a so-called ECU file. These files are stored on the local hard disk. This makes it possible to collect vehicle data, exchange them with Voith Customer Service and to archive them. With the ALADIN Delta and Fleet reports, you are able to compare different vehicles and/or compare the same vehicle at different points in time.
Apart from evaluating events, ALADIN also provides functions that support you in the maintenance and installation of a new transmission and in troubleshooting your vehicle.